From Deadlines to Timelines: Redefining Workplace Terminology for Better Well-being

Today the word "deadline" is associated with the expected delivery date of a feature or project. My dear coaching trainer •Maik Frank, PCC • shared the origin of the term—stemming from the US Civil War - in a recent discussion here on LinkedIn.

"A line drawn within or around a prison that a prisoner passes at the risk of being shot" is one of the earliest definitions.

Even though I was unaware of this cruel history, I disliked the term from the start. In my opinion, the mere mention of death unconsciously puts excessive pressure on everyone involved. I see this sentiment reflected in the results of our latest Developer Experience survey, which just came in. Many engineers complained about the pressure due to "deadlines."

eBay is important, as we support millions of sellers in making a living on our marketplace. But let's be frank—no one, neither our customers nor project participants, will die if a "deadline" is missed. I acknowledge that there are risks and consequences if a timeline is missed, and these could be severe. We could face lawsuits, miss opportunities as our competitors move faster, and more. However, it's all "just" about money; no life is on the line.

Given its incredibly cruel origin, I struggle to understand why we use this term for something as commonplace as timelines.

This is why I believe we should take a step back.

I'm asking all of you - executives, people managers, product managers, engineers, designers, and others: Please use the term "timeline" instead of "deadline."

It is less intense, and that's one more good reason to use it.

Let's discuss!

Please let's discuss on LinkedIn.